Systems and methods for managing communications across multiple identities

ABSTRACT

Electronic communications are managed across multiple identities. A user is able to create an account as well as any desired, required, or appropriate number of profiles under the account. Text messages are exchanged between users using specific profiles. For example, some text messages can be exchanged using a personal profile while other text messages need to be exchanged using a professional profile. In some instances, exchanged text messages are saved to a centralized archive. As such, one or both of the users involved in an exchange can request to retrieve some or all of the exchanged messages at a later time.

RELATED APPLICATION INFORMATION

This application is a continuation-in-part of co-pending U.S. patentapplication Ser. No. 14/473,965, filed on Aug. 29, 2014, which claimsthe benefit under 35 U.S.C. §119(e) to U.S. Provisional Application No.61/875,654, filed Sep. 9, 2013, U.S. Provisional Application No.61/875,656, filed Sep. 9, 2013, and U.S. Provisional Application No.61/875,663, filed Sep. 9, 2013, the disclosures of which areincorporated herein in their entirety.

BACKGROUND

1. Technical Field

The embodiments described herein are related to electroniccommunications and more specifically to managing multiple identities foruse in electronic communication, such as text based communication.

2. Related Art

Text messaging, or texting, generally refers to the act of sendingbrief, electronic messages between two or more devices (e.g., portabledevices such as mobile phones) over a telephone network. Although theterm initially referred to messages sent using Short Message Service(SMS), it has grown to encompass Multimedia Message Service (MMS)messages that contain a wide ranging variety of content includingimages, videos, and sound. In many situations, sending a text messagecan be far more convenient and discreet than placing a phone call.Indeed, texting has steadily supplanted voice calls as a choice means ofcommunication. By 2007, monthly texting activities have already outpacedphone calls, and as of 2012, some 80 percent of mobile phone usersreport using their devices for texting. In fact, texting is no longerrelegated to just casual or informal exchanges, and have becomeprevalent even in business and professional contexts. But despitetexting messaging's skyrocketing popularity, conventional SMS systemsstill struggle with a number of significant limitations.

First, each mobile phone is typically assigned a unique phone number(e.g., a ten digit numeric string in the United States). With aconventional SMS message, the identities of both the sender and therecipient are generally tied to the phone number associated theirrespective mobile phones. Neither party in the exchange has control orflexibility over their respective identities. As one example, imaginethat one user, Alice, is sending a text message to another user, Bob. Onthe one hand, the sending device relies on the phone number of thereceiving device in order to dispatch the text message to the correctdestination. Thus, in this example, Alice would need to have Bob's phonenumber in order to send the text message to Bob's mobile phone.Meanwhile, a receiving device will almost always be able to attribute anincoming text message to the phone number associated with the sendingdevice. So when Alice's text message is delivered, Bob's mobile phonecan recognize and inform Bob that the text message had originated fromAlice's mobile phone. To maintain more than one identity (e.g., work,personal), a user must have separate devices and a different phonenumber for each, since a single phone number cannot portedback-and-forth or otherwise shared between multiple active devices. Inpractice, most people resort to carrying one device for work and anotherdevice for personal communications. So depending on whether Alice wishesto text her colleague Bob or her friend Charlie, Alice will need toswitch between a work phone (and number) and a personal phone (andnumber).

Furthermore, many social and commercial situations warrant a disclosureor exchange of contact information although some or all of the partiesinvolved only expect or desire to stay in touch in the short-term. Phonenumbers, even temporary or disposable ones (e.g., burner phones), shouldnot be divulged indiscriminately in these situations since they aregenerally inconvenient and costly to set up and change. As one example,suppose Alice is holding a garage sale. Alice would like perspectiveshoppers to be able to contact her but only for the duration of thesale. Nevertheless, it would be impractical for Alice to set up atemporary phone number just for the garage sale but she is also loath topublicize her personal phone number when advertising her garage sale.

Conventional SMS systems also do not adequately support conversationsconducted between large groups of individuals. To the extent that a SMSmessage can be addressed to multiple recipients, group conversationsconducted via SMS tend take place only between existing acquaintances(e.g., friends, family, and colleagues). This is because the sender of aSMS message must be privy to the phone number of every participant in agroup conversation, whether the SMS message is being sent directly fromone mobile phone to another or through a SMS gateway (e.g., SMS messagessent and received as emails at a computer terminal). Consider, forinstance, a large gathering such as a sporting event or a concert.Although many people would welcome the prospect of engaging in a groupconversation with others attendees (e.g., to share personal thoughts andcommentaries), it remains largely undesirable and impractical to have toshare private phone numbers with numerous strangers.

SUMMARY

A platform that manages communications across multiple identities.

These and other features, aspects, and embodiments are described belowin the section entitled “Detailed Description.”

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and embodiments are described in conjunction with theattached drawings, in which:

FIG. 1 is a block diagram illustrating a system for managingcommunications across multiple identities according to variousembodiments;

FIG. 2 is a network diagram illustrating a network environment accordingto various embodiments;

FIG. 3A illustrates a screen display according to various embodiments;

FIG. 3B illustrates a screen display according to various embodiments;

FIG. 3C illustrates a screen display according to various embodiments;

FIG. 4 is a block diagram illustrating a device according to variousembodiments; and

FIG. 5 is a block diagram illustrating a computing environment accordingto various embodiments.

DETAILED DESCRIPTION

The embodiments disclosed herein can be implemented in numerous ways,including as a process; an apparatus; a system; a composition of matter;a computer program product embodied on a computer readable storagemedium; and/or a processor, such as a processor configured to executeinstructions stored on and/or provided by a memory coupled to theprocessor. In this specification, these example embodiments, or anyother implementations, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered. Unless statedotherwise, a component such as a processor or a memory described asbeing configured to perform a task may be implemented as a generalcomponent that is temporarily configured to perform the task at a giventime or a specific component that is manufactured to perform the task.As used herein, the term ‘processor’ refers to one or more devices,circuits, and/or processing cores configured to process data, such ascomputer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of operation. The invention is described in connection withsuch embodiments, but the invention is not limited to any embodiment.The scope of the invention is limited only by the claims and theinvention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

Various embodiments of the systems and methods described herein aredirected toward a platform that manages communications across multipleidentities. In particular, in various embodiments, the platform enablesindividual users to establish, maintain, and utilize a plurality (e.g.,two or more) of identities or profiles under a single account. Invarious embodiments, some or all of the identities are used fortext-based communication, including the sending and the receipt of textmessages. It is to be understood that a text message can include one ormore different types of data, including but not limited to images,videos, and sound. It is further to be understood that one or moredifferent types of data can be inserted in or attached to a text messagetransmitted via the platform, including but not limited to images (e.g.,.GIF, .JPEG, .BMP), files (e.g., .DOC, .PDF, .XLS, .PPT), hyperlinks,and emoticons.

FIG. 1 is a block diagram illustrating a system 100 for managingcommunications across multiple identities according to variousembodiments. In various embodiments, the system 100 includes a platform110 that communicates with a plurality of devices over a network 120. Invarious embodiments, the network 120 comprises one or more of a wirednetwork, a wireless network, a local area network, a wide area network,the Internet, or any other appropriate network. For example, in FIG. 1,the platform 110 is shown to communicate with a first device 131 (e.g.,a laptop), a second device 132 (e.g., a smartphone), and a third device133 (e.g., a tablet PC). Although only three devices (e.g., the firstdevice 131, the second device 132, and the third device 133) are shownin FIG. 1, it is to be understood that the platform 110 is capable ofcommunicating with any number of devices. Furthermore, it is to beunderstood that the platform 110 is capable of communicating with avariety of different types of devices, including but not limited to thethree that are shown in FIG. 1 (e.g., laptop, smartphone, tablet PC).

In various embodiments, the platform 110 acts as an intermediary thatroutes text messages communicated between the first device 131, thesecond device 132, and the third device 133. For example, suppose thatthe user of the first device 131, Alice, sends a text message to theusers of the second device 132 and the third device 133, Bob and Charlierespectively. In various embodiments, the text message is not delivereddirectly to the second device 132 and the third device 133. Instead, thetext message is transmitted first to the platform 110 before theplatform 110 routes the text message to the second device 132 and thethird device 133. As will be described in more detail below, in variousembodiments, the platform 110 is configured to provide a serviceenabling the users (e.g., Alice, Bob, and Charlie) of at least some ofthe first device 131, the second device 132, and the third device 133 tocommunicate (e.g., send and receive text messages) using more than oneidentity. Further as will be described in more detail below, in variousembodiments, at least some users of the first device 131, the seconddevice 132, and the third device 133 (e.g., Alice, Bob, and Charlie) cansubscribe or sign-up to the service and then communicate (e.g., send andreceive text messages) with other service subscribers and non-servicesubscribers using multiple identities. Finally, in various embodiments,the platform 110 can further act as a gateway for both incoming andoutgoing text messages. Otherwise stated, in various embodiments,messages can be sent and received in any desired, required, orappropriate communications format or protocol, including but not limitedto text messages and emails. Meanwhile, in various embodiments, the sameprofile name or handle can be used to send and to receive messagesregardless of the transmission formats or protocols. For example, Alicecan choose to send a message to Bob as either an email or a textmessage. In some embodiments, the platform 110 will automaticallyconvert and deliver as an email any text messages that exceeds a certainmaximum length (e.g., greater than 160 characters).

In various embodiments, the platform 110 stores at least some of thetest messages communicated between various devices, including the firstdevice 131, the second device 132, and the third device 133. As shown inFIG. 1, the platform 110 further communicates with a database 111. Invarious embodiments, the platform 110 is configured to archive at leastsome of the text messages routed through the platform 110 in thedatabase 111. For example, in various embodiments, the platform 110stores the text messages from Alice to both Bob and Charlie in thedatabase 111. As will be described in more detail below, the platform110 is configured to provide archival functions (e.g., latent access) toat least some of the text messages archived in the database 111.

Multi-Profile Account

The various embodiments of the systems and methods described herein aredirected toward a platform (e.g., the platform 110 described withrespect to FIG. 1) that provides a service enabling subscribers to theservice to communicate (e.g., send and receive text messages) usingmultiple identities. In particular, in various embodiments, a singleaccount can be set up to include multiple subordinate profiles. Invarious embodiments, each profile corresponds to a different identityand can be designated, assigned, or otherwise associated with adistinctive profile name or handle. In various embodiments, a user canuse different profiles to communicate with different contacts. Incontrast, one email account is generally associated with only a singleemail address. Similarly, a mobile phone is always associated with onlyone telephone number.

In the various systems and methods described herein, users are able tomaintain multiple profiles and access these profiles from differentdevices. Otherwise stated, in various embodiments, an account is notconfined to a single profile nor is a profile necessarily tied to anysingle device. In fact, in various embodiments, a user has the abilityto establish then simultaneously maintain and utilize an unlimitednumber of profiles and corresponding identities. Alice, for instance,can set up one account with at least two separate profiles. One profile(e.g., Alice@TruText.com) can be used to communicate with her friendsand family and another (e.g., Alice.Jones.Esq@TruText.com) can be usedto communicate with her colleagues at work. As such, in variousembodiments, text messages that are transmitted using a specific profileare communicated based on the corresponding profile name or handleinstead of, for example, the phone number of the sending or receivingmobile phone. For example, suppose Alice sends her friend Bob a textmessage using, Alice@TruText.com, the profile she had set up tocommunicate with friends and family. When the text message is deliveredto Bob, Bob's device (e.g., smartphone) would inform Bob that the textmessage is from Alice@TruText.com regardless of the device Alice hadused to send the text message. Should Bob subsequently respond toAlice's text message, that text message would be addressed toAlice@TruText.com and be displayed to Alice as a communication threadunder her personal profile. Advantageously, in various embodiments,every profile under one account can be accessed collectively from anyone of a user's devices. That is, in various embodiments, the user canvery quickly and easily toggle between different profiles. For example,after Alice sends one text message to Bob as Alice@TruText.com, she canswitch to her Alice.Jones.Esq@TruText.com profile to send a second textmessage to Charlie and then immediately return to her conversation withBob, all from the same device. On the other hand, to send conventionalSMS text messages from different phone numbers would entail a manualswitch from one device to another.

In various embodiments, an account is established as a result of aninitial registration, subscription, or sign-up process to the service.As such, in various embodiments, registering, subscribing, or signing upto the service generates a general, umbrella, or otherwise all-inclusiveaccount that provides a single point of nexus to a plurality ofsubordinate profiles. Advantageously, in various embodiments, multipleprofiles can be managed and manipulated at once via the account,including but not limited to adding, removing, and temporarilydecommissioning one or more profiles on the account. Furthermore, invarious embodiments, the account and every profile under the account canbe established, maintained, and utilized via from any number ofdifferent devices. In some embodiments, as part of the initialregistration or sign-up process, a user can designate one or moredevices that will be used to access the account.

For example, suppose Alice has three different devices: a smartphone, atablet PC, and a laptop. Instead of tying an account or any profileunder the account to a specific device, in various embodiments, Alice isable to access to identical features and functionalities (e.g., send andreceive text messages, add and remove profiles) with respect to heraccount and all of her profiles from any one of her devices. Toillustrate, in various embodiments, Alice is able to send and receivetext messages using her personal profile, Alice@TruText.com, whether sheis on her smartphone, tablet PC, and laptop.

FIG. 2 is a block diagram illustrating an embodiment of a networkenvironment 200 according to various embodiments. Referring to FIG. 2,the network environment 200 includes multiple devices that may be usedwith respect to a single multi-profile account.

As shown in FIG. 2, a user has configured the first device 131, thesecond device 132, and the third device 133 for use with respect to themulti-profile account. In various embodiments, the user configures a(e.g., the first device 131, the second device 132, and the third device133) by downloading and installing a copy of an application 140 on thedevice. In various embodiments, the application 140 provides a userinterface that enables a variety of interactions with the multi-profileaccount. For example, Alice can use the application 140 that isinstalled on her smartphone, the second device 132, to send a textmessage to her friend Bob using one profile (e.g., Alice@TruText.com) aswell as to send a text message to her colleague Charlie using her otherprofile (e.g., Alice.Jones.Esq@TruText.com). Alternately, Alice can alsouse the same the application 140 installed on her laptop (e.g., thefirst device 131) or tablet PC (e.g., the third device 133) to send andreceive text messages using any one of her two profiles. In variousembodiments, the application 140 provides additional features andfunctions that can be triggered, invoked, or otherwise applied withrespect to the multi-profile account, including but not limited tooptions to edit (e.g., add, remove, suspend) the profiles on Alice'saccount. As will be discussed in more detail below, the application 140also provides an interface for a user to interact with earlier textmessages that have been archived in the database 111. In variousembodiments, since the application 140 is installed on each one of thefirst device 131, the second device 132, and the third device 133, theseadditional features and functions are available on any one of the firstdevice 131, the second device 132, and the third device 133.

In some embodiments, the application 140 provides one or more GraphicUser Interface (GUI) components (e.g., text areas or fields, radiobuttons, checkboxes, drop-down menu). In various embodiments, at leastsome of the features and functions offered by the application 140 (e.g.,text messaging, profile editing) are triggered and/or executed in fullor in part based on user inputs and/or selections provided via the oneor more GUI components. For example, the GUI can include radio buttonsor drop-down menus that a user such as Alice can use to switch betweendifferent profiles. As another example, the GUI can display a text box,field, or area into which Alice can enter alpha numeric strings tocompose her text messages to either Bob or Charlie. In variousembodiments, the GUI is designed to resemble a conventional textingapplication or environment.

In various embodiments, the application 140 also provides an interfacebetween a user and the platform 110. As described with respect to FIG.1, in various embodiments, the platform 110 enables the user toestablish, maintain, and utilize the multi-profile account. In variousembodiments, at least some of the features and functions offered by theapplication 140 with respect to the multi-profile account are fully orpartially implemented by the platform 110. FIG. 2 shows that in variousembodiments, the platform 110 is in communication with the first device131, the second device 132, and the third device 133. In variousembodiments, after a user selects a particular feature or function viathe application 140 (e.g., makes a selection using the GUI), theapplication sends corresponding request(s), instruction(s), and/or datato the platform 110. For example, in some embodiments, the application140 will forward a text message originating from any one of the firstdevice 131, the second device 132, and the third device 133 first to theplatform 110 and the platform 110 then routes the text message to theappropriate destination device(s).

In various embodiments, text messages communicated between various usersare not saved locally on any individual user's devices. Advantageously,providing a centralized (e.g., cloud) storage location for text messagesis both more secure and enables users to access archived text messagesfrom any device. Returning to an earlier example, in some embodiments,the text message from Alice to Bob is saved on neither Alice's nor Bob'smobile phones. Instead, in one exemplary embodiment, text messagescommunicated between various devices are saved by the platform 110 inthe database 111. As will be discussed in more detail below, textmessages are centrally archived by the platform 110 in the database 111.In the example, Alice sends Bob a text message from one of her devicesshown in FIG. 2 (e.g., the first device 131, the second device 132, andthe third device 133). On the one hand, in various embodiments, Alice'stext message to Bob is first transmitted from her device to the platform110 where it is routed to Bob's device. In addition, in variousembodiments, the platform 110 will also save Alice's text message to Bobin Database 110.

FIG. 3A illustrates a screen display 300 that can be used inimplementing some embodiments of the systems and methods describedherein. In various embodiments, the screen display 300 shown in FIG. 3Ais displayed to users when the application 140 is initially launched. Invarious embodiments, the screen display 300 shown in FIG. 3A may be asign-in screen displayed to users when the application 140 is initiallylaunched on a device. As shown in FIG. 3A, the screen display 300 mayinclude a variety of GUI components. For example, FIG. 3A shows a firsttext input field 310 to input an account or username, a second textinput field 312 to input a password, and a “Sign In” button 314.Additionally, the screen display 300 can include a link 316 for newusers who do not have an existing account to create a new account.

In various embodiments, a user can follow the link 316 to sign up orregister for an account. In some embodiments, part of the initial signup or registration process includes designation of one or more devicesthat will be used with the account. In various embodiments, the initialsign-up or registration process also includes designation of a uniquename or handle for the account. In some embodiments, the platform 110 isconfigured to provide suggestions for an account name or handle in theevent that a desired account name or handle is already in use by anothersubscriber to the service.

It is to be understood that in various embodiments, account names areseparate and distinct from profile names or handles. In variousembodiments, the platform 110 is able to analyze the accounts andprofiles associated with various users, and decipher trends and identifycommonalties amongst different user accounts and/or profiles.Additionally, in various embodiments, the platform 110 is configured todetermine and suggest additional or alternate account and/or profilenames or handles, including account and/or profile names or handles thatcomplement a current or existing one. In some embodiments, the platform110 suggests additional or alternate account and/or profile names orhandles based on a user's characteristics (e.g., demographics). Forexample, suppose that Alice is a college graduate and is between 25-34years old. In some exemplary embodiments, the platform 110 can determinethat college graduates between the ages of 25-34 have one personalprofile, one professional or business profile, and at least fourdisposable profiles. Thus, in some embodiments, the platform 110 canrecommend that Alice create and reserve a similar set of profiles.Furthermore, in some embodiments, the platform 110 can further suggestto Alice names or handles for the personal, business, and disposableprofiles.

Furthermore, in some embodiments, an account can be set up but remaindormant or inactive. In various embodiments, a user can pay a certainfee in order to delay account activation until a later date. In variousembodiments, a user can pre-purchase one or more accounts and reservethe corresponding account names or handles in the process. In variousexemplary embodiments, account and account names or handles can be sold,traded, or otherwise transferred from one user to another. In variousembodiments, the platform 110 supports a secondary market for activeand/or inactive user accounts.

FIG. 3B illustrates a screen display 350 according to variousembodiments. In various embodiments, the screen display 350 shown inFIG. 3B is a profile selection screen displayed to users who havealready signed into their account using the application 140. As shown inFIG. 3B, in some embodiments, a selection of the names or handles atleast some of a user's active and available profiles may be shown in theupper portion of the screen display 350. In some embodiments, a user candesignate a default profile, which would be displayed upon initial logininto the account. According to FIG. 3B, a user named Eli has a firstprofile 352 (i.e., Eli_WAL), a second profile 354 (i.e., Eli_(—)34453),and a third profile 356 (i.e., West_Agile_Labs). As will be discussed inmore detail below, FIG. 3B shows that the profiles may be classifieddifferently. For example, the first profile 352 (i.e., Eli_WAL) may beclassified as “Permanent,” the second profile 354 (i.e., ELI_(—)34453)may be classified as “Temporary,” and the third profile 356 (i.e.,West_Agile_Labs) may be classified as “Group.” In addition, as will bediscussed in more detail below, one or more profiles under an accountcan be designated as a business or commercial profile.

FIG. 3B further shows that the screen display 350 may one or more GUIcomponents indicating the current selection of one or more profiles. Forexample, one or more radio buttons may appear next to each profile thatallows Eli to select any one of his three profiles. In the screendisplay 350 shown in FIG. 3B, the first profile 352 (i.e., Eli_WAL) hasbeen selected. As such, a corresponding selection of text messagescommunicated using that profile may be displayed in the lower portion ofthe profile selection screen.

Although only three profiles are shown in FIG. 3B, it is to beunderstood that in various other embodiments, Eli can simultaneouslymaintain any desired, required, or appropriate number of profiles. Insome embodiments, Eli can designate one profile (e.g., El_WAL) as adefault profile. In various embodiments, the default profile isautomatically displayed each time Eli logs or signs into his account. Insome embodiments, a user can have too many profiles to be displayedconcurrently on a single screen. In those embodiments, a scrollbar GUIcontrol component (not shown) may be added to the screen display 350shown in FIG. 3B. Likewise, a separate scrollbar GUI control component(not shown) can also be provided to enable navigation through a largenumber of text messages in the lower portion of the sample screen shownin FIG. 3B.

In various embodiments, a user can customize one or more images to bedisplayed as part of a profile on the profile selection screen. Forexample, in FIG. 3B, a corporate logo 360 for West Agile Labs appearsalong with the company's profile. Although the sample screens shown inFIGS. 3A and 3B are adapted for smartphones (e.g., the second device132), it is to be understood that similar screens are displayed on othertypes of devices, including but not limited to laptops (e.g., the firstdevice 131) and tablet PCs (e.g., the third device 133).

Disposable Profiles

In various embodiments, an account represents a more permanent constructthan the subordinate profiles. For example, the account Alice createdwhen she initially subscribed to the service will persist unless sheaffirmatively cancels or revokes her subscription to the service. Incontrast, as described with respect to FIG. 3B, some profiles under anaccount can be temporary. For example, in FIG. 3B, the Eli_(—)34453profile is a temporary profile while the Eli_WAL profile is a permanentone.

In various embodiments, a profile can be deliberately set as temporaryor disposable. As shown in FIG. 3B, in various embodiments, there are atleast three different types of profiles: permanent, temporary, andgroup. A user can, in various embodiments, set up a profile under anaccount as permanent, temporary, or group. Given the circumstances inone earlier example, Alice can set up a disposable profile (e.g.,August.Garage.Sale@TruText.com) specifically to handle inquiriesregarding her garage sale. In various embodiments, a disposable profileremains active or valid for only a limited period of time (e.g., 45days). At the end of that time period, in various embodiments, anycommunication of text messages using that temporary or disposableprofile will cease. Alice, for example, will no longer be able to sendor receive text messages using her August.Garage.Sale@TruText.comprofile once it expires.

In one exemplary embodiment, an expired temporary or disposable profileis first put on hiatus for a certain period time (e.g., 45 days) beforeit can be recycled for use by a new user. That is, in some exemplaryembodiments, an expired temporary or disposable profile will remainunavailable or otherwise inactive for an additional length of time inorder to prevent the profile's new user from inadvertently receivingtext messages intended for the profile's old user. In addition, in someexemplary embodiments, users who attempt to send text messages to anexpired temporary or disposable profile will receive an automaticresponse or notification (e.g., “This profile is not currently inuse.”). In various embodiments, an expired temporary or disposableaccount can also be renewed or extended for another period time, orconverted to a permanent profile. It is to be understood that in variousembodiments, a permanent profile does not expire automatically in thesame manner as a temporary or disposable profile. However, in variousembodiments, a permanent profile can still be deactivated orrelinquished at any time without affecting the overall account.Furthermore, it is to be understood that profiles can be transactedbetween users. That is, in various embodiments, a profile can be sold,traded, or otherwise transferred from one account to another account. Invarious embodiments, the platform 110 supports a secondary market ofuser profiles.

Business Profiles

In various embodiments, in addition to permanent, temporary, and groupprofiles, one or more profiles under an account can also be designatedas business profiles. In various embodiments, the application 140 givesusers the option to set up or designate a profile as a business profile.In some embodiments, a profile can be designated or set up as a businessprofile in addition to being a permanent, temporary, or group profile.For example, in some embodiments, Alice's profile for her garage sale(e.g., August.Garage.Sale@TruText.com) can be both a temporary and abusiness profile.

In various embodiments, when a user designates a profile as business,the application 140 is configured to prompt the user to enter additionalinformation regarding the business. In various embodiments, the user canbe prompted to provide information that includes but is not limited toan address, hours of operation, phone numbers, web addresses, andmission statements. In various embodiments, the platform 110 isconfigured to generate and publish a directory (e.g., TruText BusinessDirectory) based on information collected from a plurality ofbusinesses. In some embodiments, individual business profiles can belinked to corresponding pages on one or more review sites (e.g., Yelp®,Zagat®, AngiesList™, and Better Business Bureau®).

In various embodiments, businesses are able to advertise their productsand services via the platform 110 and through the services provided bythe platform 110. In some exemplary embodiments, some or all of theselection, timing, content, and target audience of advertisements aredetermined dynamically. For example, in one embodiment, the platform 110selectively pushes advertisements to a user's device via the application140 based on the content of the text message(s) that the user has beensending and/or receiving. Suppose that Alice and Bob are texting oneanother to set up a lunch date. In one exemplary embodiment, theplatform 110 analyzes some or all of the exchange between Alice and Bobto determine one or more relevant or appropriate advertisements forAlice and/or Bob. Since Alice and Bob are discussing a lunch date, inone exemplary embodiment, the platform 110 can determine to display toAlice and/or Bob advertisements for a local restaurant. Furthermore, inone exemplary embodiment, the advertisement can include a profile nameor handle for the restaurant (e.g., Bistro@TruText.com) that eitherAlice or Bob can use to text in a reservation.

In some embodiments, a user can set up multi-level profile names orhandles for personal or commercial uses. Advantageously, in someembodiments, multi-level profile names or handles enables a more preciserouting of text message such as within an entity or organization (e.g.,corporation, municipality). For instance, instead of simply a generalprofile name or handle for the restaurant in the previous example, therestaurant can elect more specific profile names or handles such asreservations@Bistro.TruText.com. In other examples, individual (i.e.,non-business) users can also benefit from multi-level profile names orhandles. Alice, in some embodiments, can set up profiles with names orhandles such as friends@Alice.TruText.com, family@Alice.TruText.com, andclassmates@Alice.TruText.com.

Hidden Profiles

In various embodiments, a user is able to create and utilize multipleprofiles. Moreover, the profiles may be of different types including,for example, but not limited to, permanent, temporary, and groupprofiles. For example, the user Eli can select one of the first profile352 (i.e., Eli_WAL), the second profile 354 (i.e., ELI_(—)34453), andthe third profile 356 (i.e., West_Agile_Labs) to communicate with otherusers using the selected profile as his identity.

In one exemplary embodiment, to protect a user's communication historyfrom anyone who may be viewing the user's account, the user may elect toestablish a profile that is designated as a hidden profile. In variousembodiments, the texting history associated with a hidden profile is notdirectly accessible via the application 140. For example, hiddenprofiles are not listed with other types of profiles (e.g., permanent,temporary, business, group) and cannot be searched on an account level.Hidden profiles are also not listed on the user's account history.Individual text entries associated with hidden profiles cannot be movedand archived (e.g., by the platform 110 in the database 111).

Due to the secretive nature of a hidden profile, according to oneexemplary embodiment, the existence and selection of a hidden profilecannot be indicated in an overt manner such as by using conventional GUIelements (e.g., radio buttons, dropdown menu, etc.). Instead, after auser creates a hidden profile (e.g., by selecting “hidden” as the typeof profile), the profile will not be indicated or displayed when theuser is signed into the user's account (e.g., as part of the screendisplay 350).

FIG. 3C illustrates a screen display 370 according to variousembodiments. Referring to FIG. 3C, the screen display 370 may be aprofile (or TextID) selection screen. In various embodiments, the screendisplay 370 may display one or more user profiles including, forexample, but not limited to, permanent profiles (i.e., Eli_WAL),temporary profiles (i.e., Eli_(—)34453), and group profiles (i.e.,West_Agile_Labs). As shown in FIG. 3C, the screen display 370 mayinclude one or more GUI elements that allows a user to select one of thedisplayed profiles. For example, the screen display 370 includes radiobuttons next to each profile. However, a person having ordinary skill inthe art can appreciate that a different type of GUI element (e.g., adropdown menu) may be used without departing from a scope of the presentinventive concept.

According to one exemplary embodiment, to access a hidden profile, theuser may initiate creation of a new profile such as by selecting anoption 375 (i.e., “Create New TruText ID). Upon selection of the option375, the user may be presented with a standard create screen. The usermay input “hidden” followed by the name of the previously created hiddenprofile in order to select the hidden profile for use.

Group Text Messaging

In various embodiments, a “group administrator” (i.e., any usersubscribed or registered with the platform 110) can create and designateat least one profile under an account as a group profile. In variousembodiments, a single account can accommodate any desired, required, orappropriate number of group profiles. In various embodiments, one ormore group profiles are set up in order for multiple users to engage ingroup text messaging. For example, a group profile can be set up inorder for attendees of a large event (e.g., sporting match, concert) toexchange text messages with one another without having to reveal anypersonal contact information. Instead, the name or handle of groupprofile is disseminated or publicized to some or all of the attendees.

In various embodiments, a group profile can be configured to operate inone of at least three participation modes: broadcast mode, selectivemode, and full participation mode. Suppose that a group administratorhas created a group profile (e.g., NINERSvsCHARGERS@TruText.com) forfans at a football game. In some embodiments, the group profile can beset to the broadcast participation mode. As such, in some embodiments,only the group administrator will be able to send text messages to thegroup. Meanwhile, in those embodiments, all group members remain in“listen only” mode and are not permitted to send any text messages tothe group. Alternately, in some embodiments, the group profile can beset in a selective mode. In those embodiments, the group administratorcan allow at least some of the members in the group to send textmessages to the group. In those embodiments, any number of group members(e.g., one or more) can have the privilege to broadcast text messages tothe rest of the group while the remaining group members are in the“listen only” mode. Finally, in some embodiments, the group can be setin full participation mode in which case every group member is permittedto send text messages to the entire group.

Furthermore, in some embodiments, membership to join a group textingsession can be open. Alternately, in some embodiments, a groupadministrator can impose partial or full restrictions (e.g., invitationor consent based) on group membership. Returning to theNINERSvsCHARGERS@TruText.com group profile described in the earlierexample. In some embodiments, membership to that group can be open. Thismeans that in some embodiments, any fan at the game can text a keyword(e.g., JOIN) to NINERSvsCHARGERS@TruText.com to become a member of thegroup. Conversely, group members can text a different keyword (e.g.,DROP) to NINERSvsCHARGERS@TruText.com to leave the group. In variousembodiments, text messages directed toward joining or leaving a grouptexting session are not broadcast or shared with the members of thegroup and do not become a part of the group's chat history, thread, ortranscript.

In some embodiments, a group administrator is able to conduct a pollduring a group texting session. In order to conduct a poll, the groupadministrator can include one or more questions in text messagesbroadcast to the group. For example, at the football game, the groupadministrator can send a text message to theNINERSvsCHARGERS@TruText.com group asking group members to nominate aMVP for the game. In one exemplary embodiment, text messages from groupmembers in response to the poll question(s) are not broadcast to theentire group. That is, in one exemplary embodiment, individual responsesare not shared with the group. However, in one exemplary embodiment,group members can view the collective responses or overall poll results(e.g., 32% Player A, 28% Player B, and 40% Player C).

In some embodiments, membership to join a group texting session can bemade by invitation only. That is, in some embodiments, only users whohave been specifically invited by a group administrator can become amember of the group. For example, the group administrator for theNINERSvsCHARGERS@TruText.com group can extend invitations to a selectgroup of individuals (e.g., season pass holders) to join the group. Inother embodiments, membership to a join a group texting session can becontingent upon the approval of the group administrator. For example,fans interested in communicating using the NINERSvsCHARGERS@TruText.comgroup profile must first submit a membership request to the groupadministrator and be approved by the group administrator in order toparticipate in the group texting session.

In various embodiments, group members have access to some or all of thegroup's chat transcript, thread, or history. In some embodiments, groupmembers can view only a select portion (e.g., the most recent 20minutes) of the group's chat transcript, thread, or history. In otherembodiments, group members are given access to “sliding scale” sectionsof the group's chat transcript, thread, or history. For example,although fans that have joined the NINERSvsCHARGERS@TruText.com grouptexting session have access to the group's entire chat transcript,thread, or history, only 20-minute portions of the chat transcript,thread, or history can be viewed at any one time. It is to be understoodthat in various embodiments a group administrator has the ability tochange one or both of participation and membership modes at any time.For example, the NINERSvsCHARGERS@TruText.com group can be set tooperate in the broadcast mode during gameplay but the groupadministrator can change the group to operate in the full participationmode during breaks, time-outs, and halftime. In addition, although theforegoing examples describe a single group administrator, it is to beunderstood that in various other embodiments, any number of individualscan share group administrator duties, workload, or responsibilities.That is, in some embodiments, a group texting session can be managed andmediated by more than one group administrator.

Text Message Archive

As described earlier with respect to FIGS. 1 and 2, in variousembodiments, the platform 110 is communicatively coupled with thedatabase 111. In various embodiments, the platform 110 is configured toarchive in the database 111 at least some of the text messages routedbetween users through the platform 110. For example, in variousembodiments, the platform 110 archives partial or full threads,transcripts, or histories of the text messages exchanged between Aliceand Bob. In fact, in various embodiments, the platform 110 archives atleast some of the text messages that have been sent to and from some orall of a user's separate profiles. For instance, in various embodiments,the platform 110 archives the text massages that have been sent to andfrom Alice@TruText.com and Alice.Jones.Esq@TruText.com. As such, invarious embodiments, a user like Alice can request to view any specifictext message or sets of text messages from the archives maintained inthe database 111.

In various embodiments, the application 140 provides an interface thatenables the user to send requests to the platform 110 to retrieve one ormore text messages archived in the database 111. In some embodiments,for example, the application 140 can provide a set of GUI controlelements (e.g., scrollbar, radio buttons, checkboxes, etc.) thatcorrespond to various archival functions. In some embodiments, in orderto facilitate the user's selection process, the application 140 isconfigured display or present series and/or combinations of options thatenable a user to choose individual text messages or groups of textmessages. For instance, in some embodiments, the application 140 canprompt Alice to choose from different profiles (e.g., Alice@TruText.com,Alice.Jones.Esq@TruText.com), recipients (e.g., Bob, Charlie), and/orchronologies (e.g., dates, times). As one example, Alice can select, viathe application 140, one or more text messages that were exchanged withBob using her Alice@TruText.com profile. Alternately, in anotherexample, Alice can request to view a series of text messages that shehad exchanged with Charlie on a certain date (e.g., Aug. 22, 2014) andduring a specified time period (e.g., 5-6 PM).

In various embodiments, a user's request to view a selection of earliertext messages is first transmitted to the platform 110. In variousembodiments, the platform 110 processes and responds to the request forcertain archived messages, including by retrieving the requested textmessages from the database 111 and transmitting the requested textmessages back to the user. In various embodiments, the application 140is further configured to display the request selection of archived textmessages to the user. In various embodiments, in addition or instead ofretrieving and displaying archived text messages, the application 140can provide a user the option to email or forward (via separate textmessage) a selection of one or more archived text messages.

In various embodiments, the application 140 further provides the optionto save one or more archived text messages to a folder. In variousembodiments, the user can choose either specific text messages orspecific threads of text messages to add to a folder. In variousembodiments, folders represent an organizational tool. For example, insome embodiments, Alice can create folders to store text messagesbetween her and Charlie that pertain to specific work projects. It is tobe understood that in at least some embodiments, storing one or morearchived text messages to a folder merely creates a data reference orpointer to the original storage location of the one or more textmessages in Database 110. That is, in some embodiments, storing anarchived message to a folder does not generate an additional copy of thetext message or cause a change in actual data storage location. In someembodiments, the application 140 provides each user at least onestandard or default folder. In one exemplary embodiment, the application140 additionally or alternately permits users to create one or morecustom or personalized folders and/or sub-folders.

Non-Registered Users

In various embodiments, a registered user can both send and receive textmessages from someone who is not registered to use the services providedby the platform 110. A non-registered sender can, in variousembodiments, simply send a text or email message to a registered userusing any one of the registered user's profile names or handles. SupposeDave is not registered with the platform 110, in various embodiments, hewould send a message to either Alice@TruText.com orAlice.Jones.Esq@TruText.com as he would a SMS text message or an email.

In some embodiments, a text message from a registered user to anon-registered recipient is delivered to the non-registered recipient asa conventional email or text message. That is, in some embodiments, theplatform 110 acts as a gateway in routing the message between the twoparties, including by converting the text message from the registeredusers into an email or a SMS text message. In other embodiments, insteadof the actual message from the registered user, the platform 110delivers instead a notification message to the non-registered recipient.In some embodiments, the notification message can include a portion ofthe original text message from the registered user. Alternately or inaddition, in various embodiments, the notification message can includean invitation to the non-registered recipient to sign-up or register forthe services provided by the platform 110. In some embodiments, in orderto view the text message, a non-registered recipient must sign-up orregister for the services provided by the platform 110. In otherembodiments, a non-registered recipient can choose to bypass the sign-upor registration process. In one embodiment, instead of signing up orregistering for the service, the non-registered recipient can requestthat the text message from the registered user be forwarded via analternate medium (e.g., SMS text message, email). In another embodiment,the non-registered recipient can bypass the sign-up or registration, andstill download and install a limited-function application in order toview the text message from the registered user. In various embodiments,the limited-function application is a condensed, abridged, or shellversion of the application 140 (e.g., the application 140 Lite). Invarious embodiments, the lite version of the application 140 provides alimited roster of only basic functionalities such as viewing or replyingto a text message from a registered user.

FIG. 4 is a block diagram illustrating a device 400 according to variousembodiments. In some embodiments, the device 400 can be used toimplement any of the first device 131, the second device 132, and thethird device 133 described with respect to FIGS. 1 and 2. In variousembodiments, the device 400 can be used as is or in conjunction with oneor more of the mechanisms or processes described above, and canrepresent components of server(s), user system(s), and/or other devicesdescribed herein. The device 400 can be a server or any conventionalpersonal computer, or any other processor-enabled device that is capableof wired or wireless data communication. Other computer systems and/orarchitectures can be also used, as will be clear to those skilled in theart.

The device 400 preferably includes one or more processors, such as aprocessor 410. Additional processors can be provided, such as anauxiliary processor to manage input/output, an auxiliary processor toperform floating point mathematical operations, a special-purposemicroprocessor having an architecture suitable for fast execution ofsignal processing algorithms (e.g., digital signal processor), a slaveprocessor subordinate to the main processing system (e.g., back-endprocessor), an additional microprocessor or controller for dual ormultiple processor systems, or a coprocessor. Such auxiliary processorscan be discrete processors or can be integrated with the processor 410.Examples of processors which can be used with the device 400 include,without limitation, the Pentium® processor, Core i7® processor, andXeon® processor, all of which are available from Intel Corporation ofSanta Clara, Calif.

The processor 410 is preferably connected to a communication bus 405.Communication Bus 405 can include a data channel for facilitatinginformation transfer between storage and other peripheral components ofthe device 400. The communication bus 405 further can provide a set ofsignals used for communication with the processor 410, including a databus, address bus, and control bus (not shown). The communication bus 405can comprise any standard or non-standard bus architecture such as, forexample, bus architectures compliant with industry standard architecture(ISA), extended industry standard architecture (EISA), Micro ChannelArchitecture (MCA), peripheral component interconnect (PCI) local bus,or standards promulgated by the Institute of Electrical and ElectronicsEngineers (IEEE) including IEEE 488 general-purpose interface bus(GPIB), IEEE 696/S-100, and the like.

The device 400 preferably includes a main memory 415 and can alsoinclude a secondary memory 420. The main memory 415 provides storage ofinstructions and data for programs executing on the processor 410, suchas one or more of the functions and/or modules discussed above. Itshould be understood that programs stored in the memory and executed bythe processor 410 can be written and/or compiled according to anysuitable language, including without limitation C/C++, Java, JavaScript,Pearl, Visual Basic, .NET, and the like. The main memory 415 istypically semiconductor-based memory such as dynamic random accessmemory (DRAM) and/or static random access memory (SRAM). Othersemiconductor-based memory types include, for example, synchronousdynamic random access memory (SDRAM), Rambus dynamic random accessmemory (RDRAM), ferroelectric random access memory (FRAM), and the like,including read only memory (ROM).

The secondary memory 420 can optionally include an internal memory 425and/or a removable storage medium 430, for example a floppy disk drive,a magnetic tape drive, a compact disc (CD) drive, a digital versatiledisc (DVD) drive, other optical drive, a flash memory drive, etc. Theremovable storage medium 430 is read from and/or written to in awell-known manner. The removable storage medium 430 can be, for example,a floppy disk, magnetic tape, CD, DVD, SD card, etc.

The removable storage medium 430 can be a non-transitorycomputer-readable medium having stored thereon computer executable code(i.e., software) and/or data (e.g., for implementing at least a portionof the subject matter described herein). The computer software or datastored on the removable storage medium 430 is read into the device 400for execution by the processor 410.

In alternative embodiments, the secondary memory 420 can include othersimilar means for allowing computer programs or other data orinstructions to be loaded into the device 400. Such means can include,for example, an external storage medium 445 and an interface 440.Examples of the external storage medium 445 can include an external harddisk drive or an external optical drive, or and external magneto-opticaldrive.

Other examples of the secondary memory 420 can includesemiconductor-based memory such as programmable read-only memory (PROM),erasable programmable read-only memory (EPROM), electrically erasableread-only memory (EEPROM), or flash memory (block oriented memorysimilar to EEPROM). Also included are any other forms of the removablestorage media 430 and the communication interface 440, which allowsoftware and data to be transferred from an external medium 445 to thedevice 400.

The device 400 can include a communication interface 440. Thecommunication interface 440 allows software and data to be transferredbetween the device 400 and external devices (e.g. printers), networks,or information sources. For example, computer software or executablecode can be transferred to the device 400 from a network server via thecommunication interface 440. Examples of the communication interface 440include a built-in network adapter, network interface card (NIC),Personal Computer Memory Card International Association (PCMCIA) networkcard, card bus network adapter, wireless network adapter, UniversalSerial Bus (USB) network adapter, modem, a network interface card (NIC),a wireless data card, a communications port, an infrared interface, anIEEE 1394 fire-wire, or any other device capable of interfacing thedevice 400 with a network or another computing device.

The communication interface 440 preferably implements industrypromulgated protocol standards, such as Ethernet IEEE 802 standards,Fiber Channel, digital subscriber line (DSL), asynchronous digitalsubscriber line (ADSL), frame relay, asynchronous transfer mode (ATM),integrated digital services network (ISDN), personal communicationsservices (PCS), transmission control protocol/Internet protocol(TCP/IP), serial line Internet protocol/point to point protocol(SLIP/PPP), and so on, but can also implement customized or non-standardinterface protocols as well.

Software and data transferred via the communication interface 440 aregenerally in the form of electrical communication signals 455. Suchsignals 455 are preferably provided to the communication interface 440via a communication channel 450. In one embodiment, the communicationchannel 450 can be a wired or wireless network, or any variety of othercommunication links. The communication channel 450 carries signals 455and can be implemented using a variety of wired or wirelesscommunication means including wire or cable, fiber optics, conventionalphone line, cellular phone link, wireless data communication link, radiofrequency (“RF”) link, or infrared link, just to name a few.

Computer executable code (i.e., computer programs or software) is storedin the main memory 415 and/or the secondary memory 420. Computerprograms can also be received via the communication interface 440 andstored in the main memory 415 and/or the secondary memory 420. Suchcomputer programs, when executed, enable the device 400 to perform thevarious functions, such as those described herein.

In this description, the term “computer readable medium” is used torefer to any non-transitory computer readable storage media used toprovide computer executable code (e.g., software and computer programs)to the device 400. Examples of these media include the main memory 415,the secondary memory 420 (including the internal memory 425, theremovable medium 430, and the external storage medium 445), and anyperipheral device communicatively coupled with the communicationinterface 440 (including a network information server or other networkdevice). These non-transitory computer readable mediums are means forproviding executable code, programming instructions, and software to thedevice 400.

In an embodiment that is implemented using software, the software can bestored on a computer readable medium and loaded into the device 400 byway of the removable medium 430, an I/O interface 435, or acommunication interface 440. In such an embodiment, the software isloaded into the device 400 in the form of electrical communicationSignals 455. The software, when executed by the processor 410,preferably causes the processor 410 to perform the inventive featuresand functions previously described herein.

In an embodiment, the I/O interface 435 provides an interface betweenone or more components of the device 400 and one or more input and/oroutput devices. Example input devices include, without limitation,keyboards, touch screens or other touch-sensitive devices, biometricsensing devices, computer mice, trackballs, pen-based pointing devices,camera, microphone, and the like. Examples of output devices include,without limitation, cathode ray tubes (CRTs), plasma displays,light-emitting diode (LED) displays, liquid crystal displays (LCDs),printers, vacuum florescent displays (VFDs), surface-conductionelectron-emitter displays (SEDs), field emission displays (FEDs), andthe like.

The device 400 also includes optional wireless communication componentsthat facilitate wireless communication over a voice and over a datanetwork. The wireless communication components can comprise an antennasystem 460, a radio system 465, a baseband system 470, or anycombination thereof. In the device 400, radio frequency (RF) signals aretransmitted and received over the air by the antenna system 460 underthe management of the radio system 465.

In one embodiment, the antenna system 460 can comprise one or moreantennae and one or more multiplexors (not shown) that perform aswitching function to provide the antenna system 460 with transmit andreceive signal paths. In the receive path, received RF signals can becoupled from a multiplexor to a low noise amplifier (not shown) thatamplifies the received RF signal and sends the amplified signal to theradio system 465.

In alternative embodiments, the radio system 465 can comprise one ormore radios that are configured to communicate over various frequencies.In one embodiment, the radio system 465 can combine a demodulator (notshown) and modulator (not shown) in one integrated circuit (IC). Thedemodulator and modulator can also be separate components. In theincoming path, the demodulator strips away the RF carrier signal leavinga baseband receive audio signal, which is sent from the radio system 465to the baseband system 470.

If the received signal contains audio information, the baseband system470 decodes the signal and converts it to an analog signal. Then thesignal is amplified and sent to a speaker. The baseband system 470 alsoreceives analog audio signals from a microphone. These analog audiosignals are converted to digital signals and encoded by the basebandsystem 470. The baseband system 470 also codes the digital signals fortransmission and generates a baseband transmit audio signal that isrouted to the modulator portion of the radio system 465. The modulatormixes the baseband transmit audio signal with an RF carrier signalgenerating an RF transmit signal that is routed to the antenna systemand can pass through a power amplifier (not shown). The power amplifieramplifies the RF transmit signal and routes it to the Antenna System 460where the signal is switched to the antenna port for transmission.

The baseband system 470 is also communicatively coupled with theprocessor 410. The processor 410 has access to the main memory 415 andthe secondary memory 420. The processor 410 is preferably configured toexecute instructions (i.e., computer programs or software) that can bestored in the main memory 415 or the secondary memory 420. Computerprograms can also be received from the baseband processor 460 and storedin the main memory 415 or in the secondary memory 420, or be executedupon receipt. Such computer programs, when executed, enable the device400 to perform the various functions, such as those described herein.For example, the main memory 415 and secondary memory 420 can eachinclude various software modules (not shown).

Various embodiments may also be implemented primarily in hardware using,for example, components such as application specific integrated circuits(ASICs), or field programmable gate arrays (FPGAs). Implementation of ahardware state machine capable of performing the functions describedherein will also be apparent to those skilled in the relevant art.Various embodiments may also be implemented using a combination of bothhardware and software.

Furthermore, those of skill in the art will appreciate that the variousillustrative logical blocks, modules, circuits, and method stepsdescribed in connection with the above described figures and theembodiments disclosed herein can often be implemented as electronichardware, computer software, or combinations of both. To clearlyillustrate this interchangeability of hardware and software, variousillustrative components, blocks, modules, circuits, and steps have beendescribed above generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled persons can implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the invention. In addition, the grouping of functions within amodule, block, circuit or step is for ease of description. Specificfunctions or steps can be moved from one module, block or circuit toanother without departing from the invention.

Moreover, the various illustrative logical blocks, modules, functions,and methods described in connection with the embodiments disclosedherein can be implemented or performed with a general purpose processor,a digital signal processor (DSP), an ASIC, FPGA or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor can be a microprocessor,but in the alternative, the processor can be any processor, controller,microcontroller, or state machine. A processor can also be implementedas a combination of computing devices, for example, a combination of aDSP and a microprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration.

Additionally, the steps of a method or algorithm described in connectionwith the embodiments disclosed herein can be embodied directly inhardware, in a software module executed by a processor, or in acombination of the two. A software module can reside in RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, harddisk, a removable disk, a CD-ROM, or any other form of storage mediumincluding a network storage medium. An exemplary storage medium can becoupled to the processor such the processor can read information from,and write information to, the storage medium. In the alternative, thestorage medium can be integral to the processor. The processor and thestorage medium can also reside in an ASIC.

FIG. 5 illustrates a computing environment 500 according to variousembodiments. Referring to FIG. 5, in various embodiments, the computingenvironment 500 may include a Computing Device 505 (e.g., servers) thatis suitable for use in some embodiments of the systems and methodsdescribed herein. One or more Computing Device 505 can be used toimplement the platform 110. Computing Device 505 in ComputingEnvironment 500 can include one or more processing units, cores, orProcessors 510, Memory 515 (e.g., RAM, ROM, and/or the like), InternalStorage 520 (e.g., magnetic, optical, solid state storage, and/ororganic), and/or I/O Interface 525, any of which can be coupled on acommunication mechanism or Bus 530 for communicating information orembedded in the Computing Device 505.

Computing Device 505 can be communicatively coupled to Input/UserInterface 535 and Output Device/Interface 540. Either one or both ofInput/User Interface 535 and Output Device/Interface 540 can be a wiredor wireless interface and can be detachable. Input/User Interface 535can include any device, component, sensor, or interface, physical orvirtual, that can be used to provide input (e.g., buttons, touch-screeninterface, keyboard, a pointing/cursor control, microphone, camera,braille, motion sensor, optical reader, and/or the like). OutputDevice/Interface 540 can include a display, television, monitor,printer, speaker, braille, or the like. In some example implementations,Input/User Interface 535 and Output Device/Interface 540 can be embeddedwith or physically coupled to Computing Device 505. In other exampleimplementations, other computing devices can function as or provide thefunctions of Input/User Interface 535 and Output Device/Interface 540for Computing Device 505.

Examples of Computing Device 505 can include, but are not limited to,highly mobile devices (e.g., smartphones, devices in vehicles and othermachines, devices carried by humans and animals, and the like), mobiledevices (e.g., tablets, notebooks, laptops, personal computers, portabletelevisions, radios, and the like), and devices not designed formobility (e.g., desktop computers, other computers, information kiosks,televisions with one or more processors embedded therein and/or coupledthereto, radios, and the like).

Computing Device 505 can be communicatively coupled (e.g., via I/OInterface 525) to External Storage 545 and Network 550 for communicatingwith any number of networked components, devices, and systems, includingone or more computing devices of the same or different configuration.Computing Device 505 or any connected computing device can befunctioning as, providing services of, or referred to as a server,client, thin server, general machine, special-purpose machine, oranother label.

I/O Interface 525 can include, but is not limited to, wired and/orwireless interfaces using any communication or I/O protocols orstandards (e.g., Ethernet, 802.11x, Universal System Bus, WiMax, modem,a cellular network protocol, and the like) for communicating informationto and/or from at least all the connected components, devices, andnetwork in Computing Environment 500. Network 550 can be any network orcombination of networks (e.g., the Internet, local area network, widearea network, a telephonic network, a cellular network, satellitenetwork, and the like).

Computing Device 505 can use and/or communicate using computer-usable orcomputer-readable media, including transitory media and non-transitorymedia. Transitory media include transmission media (e.g., metal cables,fiber optics), signals, carrier waves, and the like. Non-transitorymedia include magnetic media (e.g., disks and tapes), optical media(e.g., CD ROM, digital video disks, Blu-ray disks), solid state media(e.g., RAM, ROM, flash memory, solid-state storage), and othernon-volatile storage or memory.

Computing Device 505 can be used to implement techniques, methods,applications, processes, or computer-executable instructions in someexample computing environments. Computer-executable instructions can beretrieved from transitory media, and stored on and retrieved fromnon-transitory media. The executable instructions can originate from oneor more of any programming, scripting, and machine languages (e.g., C,C++, C#, Java, Visual Basic, Python, Perl, JavaScript, and others).

Processor(s) 510 can execute under any operating system (OS) (notshown), in a native or virtual environment. One or more applications canbe deployed that include Logic Unit 560, Application ProgrammingInterface (API) unit 565, Input Unit 570, Output Unit 575, UserManagement 580, Information Exchange Module 585, and Database 590,Inter-Unit Communication Mechanism 595 for the different units tocommunicate with each other, with the OS, and with other applications(not shown). The described units and elements can be varied in design,function, configuration, or implementation and are not limited to thedescriptions provided.

In some example implementations, when information or an executioninstruction is received by API Unit 565, it can be communicated to oneor more other units (e.g., Logic Unit 560, Input Unit 570, Output Unit575, User Management 580, Information Exchange Module 585, and Database590). For example, after Input Unit 570 has received, via Network 550,device MAC addresses and/or user information, Input Unit 570 can use APIUnit 565 to communicate the information to User Management 580. UserManagement 580 can, via API Unit 565, interact with the Logic Unit 360to store or update in Database 590 correlated data between individualuser information and corresponding MAC addresses of each user's device.User Management 580 also can, via API Unit 565, interact with Logic Unit360 to retrieve from Database 590 individual user information thatcorresponds to specific device MAC addresses. Output Unit 575 cansubsequently transmit the individual user information via Network 550.

In some instances, Logic Unit 560 can be configured to control theinformation flow among the units and direct the services provided by APIUnit 565, Input Unit 570, Output Unit 575, User Management 580, andDatabase 590. For example, the flow of one or more processes orimplementations can be controlled by Logic Unit 560 alone or inconjunction with API Unit 565.

In situations in which the systems discussed here collect personalinformation about users, or can make use of personal information, theusers can be provided with an opportunity to control whether programs orfeatures collect user information (e.g., information about a user'ssocial network, social actions or activities, profession, a user'spreferences, or a user's current location), or to control whether and/orhow to receive content from the content server that can be more relevantto the user. In addition, certain data can be treated in one or moreways before it is stored or used, so that personally identifiableinformation is removed. For example, a user's identity can be treated sothat no personally identifiable information can be determined for theuser, or a user's geographic location can be generalized where locationinformation is obtained (such as to a city, ZIP code, or state level),so that a particular location of a user cannot be determined. Thus, theuser can have control over how information is collected about the userand used by a content server.

Any of the software components described herein may take a variety offorms. For example, a component may be a stand-alone software package,or it may be a software package incorporated as a “tool” in a largersoftware product. It may be downloadable from a network, for example, awebsite, as a stand-alone product or as an add-in package forinstallation in an existing software application. It may also beavailable as a client-server software application, as a web-enabledsoftware application, and/or as a mobile application.

Although a few example implementations have been shown and described,these example implementations are provided to convey the subject matterdescribed herein to people who are familiar with this field. It shouldbe understood that the subject matter described herein may beimplemented in various forms without being limited to the describedexample implementations. The subject matter described herein can bepracticed without those specifically defined or described matters orwith other or different elements or matters not described. It will beappreciated by those familiar with this field that changes can be madein these example implementations without departing from the subjectmatter described herein as defined in the appended claims and theirequivalents.

Various embodiments may also be implemented primarily in hardware using,for example, components such as application specific integrated circuits(ASICs), or field programmable gate arrays (FPGAs). Implementation of ahardware state machine capable of performing the functions describedherein will also be apparent to those skilled in the relevant art.Various embodiments may also be implemented using a combination of bothhardware and software.

Furthermore, those of skill in the art will appreciate that the variousillustrative logical blocks, modules, circuits, and method stepsdescribed in connection with the above described figures and theembodiments disclosed herein can often be implemented as electronichardware, computer software, or combinations of both. To clearlyillustrate this interchangeability of hardware and software, variousillustrative components, blocks, modules, circuits, and steps have beendescribed above generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled persons can implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the invention. In addition, the grouping of functions within amodule, block, circuit or step is for ease of description. Specificfunctions or steps can be moved from one module, block or circuit toanother without departing from the invention.

Moreover, the various illustrative logical blocks, modules, functions,and methods described in connection with the embodiments disclosedherein can be implemented or performed with a general purpose processor,a digital signal processor (DSP), an ASIC, FPGA or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor can be a microprocessor,but in the alternative, the processor can be any processor, controller,microcontroller, or state machine. A processor can also be implementedas a combination of computing devices, for example, a combination of aDSP and a microprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration.

Additionally, the steps of a method or algorithm described in connectionwith the embodiments disclosed herein can be embodied directly inhardware, in a software module executed by a processor, or in acombination of the two. A software module can reside in RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, harddisk, a removable disk, a CD-ROM, or any other form of storage mediumincluding a network storage medium. An exemplary storage medium can becoupled to the processor such the processor can read information from,and write information to, the storage medium. In the alternative, thestorage medium can be integral to the processor. The processor and thestorage medium can also reside in an ASIC.

Any of the software components described herein may take a variety offorms. For example, a component may be a stand-alone software package,or it may be a software package incorporated as a “tool” in a largersoftware product. It may be downloadable from a network, for example, awebsite, as a stand-alone product or as an add-in package forinstallation in an existing software application. It may also beavailable as a client-server software application, as a web-enabledsoftware application, and/or as a mobile application.

While certain embodiments have been described above, it will beunderstood that the embodiments described are by way of example only.Accordingly, the systems and methods described herein should not belimited based on the described embodiments. Rather, the systems andmethods described herein should only be limited in light of the claimsthat follow when taken in conjunction with the above description andaccompanying drawings.

What is claimed:
 1. A system for managing communications across aplurality of identities, the system comprising: a messaging servercomprising a processor configured to: receive, from a first user, arequest to create a first account; create, in response to one or moreindications from the first user, a first profile and a second profileassociated with the first account, wherein the first profile isdesignated by the first user as a hidden profile; provide, as part of aselection screen displayed to the first user, the second profile but notthe first profile; receive, from the first user, a selection of thesecond profile and one or more messages from the first user to a seconduser using the second profile; transmit the one or more messages fromthe first user to the second user using the second profile; and archivethe one or more messages; a memory coupled to the processor andconfigured to provide the processor with instructions.
 2. The system ofclaim 1, wherein the second profile comprises a permanent profile. 3.The system of claim 1, wherein the second profile comprises a temporaryprofile that expires after a predetermined amount of time.
 4. The systemof claim 3, wherein the processor is further configured to suspend anexpired temporary profile for a predetermined amount of time before theexpired temporary profile can be used by a third user.
 5. The system ofclaim 1, wherein the second profile comprises a group profile.
 6. Thesystem of claim 5, wherein the processor is further configured tocommunicate messages amongst a plurality of users using the groupprofile.
 7. The system of claim 1, wherein the second profile comprisesa business profile.
 8. The system of claim 7, wherein the processor isfurther configured to request, from the first user, informationassociated with the business profile.
 9. The system of claim 8, whereinthe information associated with the business profile includes one ormore of the following: an address, an hour of operation, a telephonenumber, a web address, and a mission statement.
 10. The system of claim1, wherein at least one of the first profile and the second profile isaccessible by the first user using any one of a plurality of devices.11. The system of claim 10, wherein the processor is further configuredto register at least one of the plurality of devices for use with theaccount.
 12. The system of claim 1, wherein the processor is furtherconfigured to respond to a request from the first user to retrieve atleast one archived message associated with the second profile.
 13. Thesystem of claim 12, wherein in response to the request, the processor isconfigured to transmit the at least one archived message to the firstuser.
 14. The system of claim 13, wherein the processor is configured totransmit the at least one archived message using one or more of thefollowing: an email, a text message, and social media.
 15. The system ofclaim 1, wherein the processor is configured to provide access to thefirst profile in response to the first user's indication to create a newprofile and input of a name associated with the first profile.
 16. Amethod for managing communications across a plurality of identities, themethod comprising: receiving, from a first user, a request to create afirst account; using a processor to create, in response to one or moreindications from the first user, a first profile and a second profileassociated with the first account, wherein the first profile isdesignated by the first user as a hidden profile; providing, as part ofa selection screen displayed to the first user, access to the secondprofile but not the first profile; receiving, from the first user, aselection of the second profile and one or more messages from the firstuser to a second user using the second profile; transmitting the one ormore messages from the first user to the second user using the secondprofile; and archiving the one or more messages.
 17. The method of claim16, wherein the second profile comprises a permanent profile.
 18. Themethod of claim 16, wherein the second profile comprises a temporaryprofile that expires after a predetermined amount of time.
 19. Themethod of claim 18, further comprising suspending an expired temporaryprofile for a predetermined amount of time before the expired temporaryprofile can be used by a third user.
 20. The method of claim 16, whereinthe second profile comprises a group profile.
 21. The method of claim20, further comprising communicating messages amongst a plurality ofusers using the group profile.
 22. The method of claim 16, wherein thesecond profile comprises a business profile.
 23. The method of claim 22,further comprising requesting, from the first user, informationassociated with the business profile.
 24. The method of claim 23,wherein the information associated with the business profile thatincludes one or more of the following: an address, an hour of operation,a telephone number, a web address, and a mission statement.
 25. Themethod of claim 16, wherein at least one of the first profile and thesecond profile is accessible by the first user using any one of aplurality of devices.
 26. The method of claim 25, further comprisingregistering at least one of the plurality of devices for use with theaccount.
 27. The method of claim 16, further comprising responding to arequest from the first user to retrieve at least one archived message.28. The method of claim 27, wherein responding to the request includestransmitting the at least one archived message to the first user. 29.The method of claim 28, wherein the at least one archived message istransmitted to the first user using one or more of the following: anemail, a text message, and social media.
 30. The method of claim 15,further comprising providing access to the first profile in response tothe first user's indication to create a new profile and input of a nameassociated with the first profile.